Architecture for manufacturing authenticatable gaming systems

ABSTRACT

An architecture is described to manufacture console-based gaming systems in a manner that allows them to be authenticated to a remote entity for online participation. The architecture involves placing pre-established secrets on the game console during console manufacturing that may be subsequently used to guarantee the authenticity of the game console during registration time.

TECHNICAL FIELD

This invention relates to console-based gaming systems, and moreparticularly, to systems and methods for manufacturing game consolesthat can be authenticated for participation in online services such asonline gaming.

BACKGROUND

Traditionally, gaming systems with a dedicated console were standalonemachines that accommodated a limited number of players (e.g., 4).PC-based gaming grew in popularity in part due to the ability to playgames online with many remote players over a network (e.g., theInternet). Thus, one trend for dedicated gaming systems is to providebroadband capabilities to facilitate online gaming.

Creating an online gaming architecture for dedicated consoles posesseveral unique and difficult problems. One problem is that there are anumber of hackers that constantly attempt to cheat during online gamesto gain various gaming advantages. To defeat this cheating, varioussecurity schemes are deployed to protect the data being transmitted overthe network from hacker observation and/or modification. Such schemes,however, require the game console to authenticate itself with a remoteentity (e.g., online gaming server, registration server, other playersystem, etc.). Valid credentials are used during authentication toguarantee authenticity of network traffic during gaming. If thesecredentials could be easily obtained during registration, a hacker couldeasily manipulate the credentials and forge all network packets from thevideo game console using another computer. From the game server'sperspective, the gaming packets appear to be authentic since it camefrom a network source that was capable of providing the requiredcredentials.

Accordingly, to secure online gaming and other services, there is a needto prevent hackers from easily obtaining valid credentials for purposesof cheating or other improper uses.

SUMMARY

An architecture for manufacturing console-based gaming systems involvesplacing pre-established secrets on a game console during manufacturingand subsequently using the secrets to guarantee the authenticity of thegame console during registration time.

Two representative implementations are described: a symmetric keyarchitecture and a public key architecture. The former architectureinvolves writing a randomly generated symmetric key, along with aconsole ID, into programmatically accessible non volatile memory of thegame console during manufacturing. The symmetric key is encrypted usinga public key during transport. The corresponding private key, and theencrypted symmetric key, are securely maintained at an authenticationentity.

During registration, the game console submits the key (or proof of keyknowledge) and the console ID pair to the authentication entity. Thepair functions as a password/name pair to locate the correspondingsymmetric key maintained at the authentication entity. The private keyis then used to decrypt the symmetric key. The key submitted by the gameconsole is evaluated against the recovered symmetric key as a way todetermine whether the console is authentic.

The public key architecture involves writing a private key and a digitalcertificate into each game console during manufacturing. The certificatecontains the public key corresponding to the private key. Thecertificate is part of a certificate chain that includes a certificationauthority certificate associated with a certification authority at eachmanufacturing site and a root certificate from which the certificationauthority certificate is derived. Whenever a game console goes onlinefor registration, a certificate chain verification process along withproof of knowledge of the private key stored on the game console areused to authenticate the console as genuine.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a gaming system with a game console and one or morecontrollers.

FIG. 2 is a block diagram of the gaming system.

FIG. 3 illustrates a network gaming system in which the FIG. 1 gamingsystem is connected via a network to other consoles, services, and aticket issuing entity.

FIG. 4 illustrates a manufacturing process in which a symmetric key anda console ID are placed on the game console during manufacturing.

FIG. 5 illustrates a registration process in which an authenticationserver authenticates the game console using the symmetric key andconsole ID.

FIG. 6 illustrates a pre-manufacturing process in which public key pairsand chained certificates are initially generated.

FIG. 7 illustrates a manufacturing process in which a private key andone or more certificates are placed on the game console duringmanufacturing.

FIG. 8 illustrates a registration process in which the authenticationserver authenticates the game console using the private key and acertificate verification process.

DETAILED DESCRIPTION

The following discussion is directed to console-based gaming systemswith online connectivity and techniques for manufacturing such gamingsystems in a manner that they can be authenticated by a remoteauthentication entity over an open network, such as the Internet. Thetechniques address the problem of how the authentication entity can beassured that the entity on the other side of the network is anauthorized gaming system.

The discussion assumes that the reader is familiar with basiccryptography principles, such as encryption, decryption, authentication,hashing, digital signatures, and digital certificates. For a basicintroduction to cryptography, the reader is directed to a text writtenby Bruce Schneier and entitled, “Applied Cryptography: Protocols,Algorithms, and Source Code in C,” published by John Wiley & Sons,copyright 1994 (second edition 1996), which is hereby incorporated byreference.

Gaming System

FIG. 1 shows an exemplary gaming system 100. It includes a game console102 and up to four controllers, as represented by controllers 104(1) and104(2). The game console 102 is equipped with an internal hard diskdrive and a portable media drive 106 that supports various forms ofportable storage media as represented by optical storage disc 108.Examples of suitable portable storage media include DVD, CD-ROM, gamediscs, game cartridges, and so forth.

The game console 102 has four slots 110 on its front face to support upto four controllers, although the number and arrangement of slots may bemodified. A power button 112 and an eject button 114 are also positionedon the front face of the game console 102. The power button 112 switchespower to the game console and the eject button 114 alternately opens andcloses a tray of the portable media drive 106 to allow insertion andextraction of the storage disc 108.

The game console 102 connects to a television or other display (notshown) via A/V interfacing cables 120. A power cable 122 provides powerto the game console. The game console 102 may further be configured withbroadband capabilities, as represented by the cable or modem connector124 to facilitate access to a network, such as the Internet.

Each controller 104 is coupled to the game console 102 via a wire orwireless interface. In the illustrated implementation, the controllersare USB (Universal Serial Bus) compatible and are connected to theconsole 102 via serial cables 130. The controller 102 may be equippedwith any of a wide variety of user interaction mechanisms. Asillustrated in FIG. 1, each controller 104 is equipped with twothumbsticks 132(1) and 132(2), a D-pad 134, buttons 136, and twotriggers 138. These mechanisms are merely representative, and otherknown gaming mechanisms may be substituted for or added to those shownin FIG. 1.

A memory unit (MU) 140 may be inserted into the controller 104 toprovide additional and portable storage. Portable memory units enableusers to store game parameters and port them for play on other consoles.In the described implementation, each controller is configured toaccommodate two memory units 140, although more or less than two unitsmay be employed in other implementations.

The gaming system 100 is capable of playing, for example, games, music,and videos. With the different storage offerings, titles can be playedfrom the hard disk drive or the portable medium 108 in drive 106, froman online source, or from a memory unit 140. A sample of what the gamingsystem 100 is capable of playing back include:

-   -   1. Game titles played from CD and DVD discs, from the hard disk        drive, or from an online source.    -   2. Digital music played from a CD in the portable media drive        106, from a file on the hard disk drive (e.g., Windows Media        Audio (WMA) format), or from online streaming sources.    -   3. Digital audio/video played from a DVD disc in the portable        media drive 106, from a file on the hard disk drive (e.g.,        Active Streaming Format), or from online streaming sources.

FIG. 2 shows functional components of the gaming system 100 in more 19detail. The game console 102 has a central processing unit (CPU) 200 anda memory controller 202 that facilitates processor access to varioustypes of memory, including a flash ROM (Read Only Memory) 204, a RAM(Random Access Memory) 206, a hard disk drive 208, and the portablemedia drive 106. The CPU 200 is equipped with a level 1 cache 210 and alevel 2 cache 212 to temporarily store data and hence reduce the numberof memory access cycles, thereby improving processing speed andthroughput.

The CPU 200, memory controller 202, and various memory devices areinterconnected via one or more buses, including serial and parallelbuses, a memory bus, a peripheral bus, and a processor or local bususing any of a variety of bus architectures. By way of example, sucharchitectures can include an Industry Standard Architecture (ISA) bus, aMicro Channel Architecture (MCA) bus, an Enhanced ISA (EISA) bus, aVideo Electronics Standards Association (VESA) local bus, and aPeripheral Component Interconnects (PCI) bus.

As one suitable implementation, the CPU 200, memory controller 202, ROM204, and RAM 206 are integrated onto a common module 214. In thisimplementation, ROM 204 is configured as a flash ROM that is connectedto the memory controller 202 via a PCI (Peripheral ComponentInterconnect) bus and a ROM bus (neither of which are shown). RAM 206 isconfigured as multiple DDR SDRAM (Double Data Rate Synchronous DynamicRAM) that are independently controlled by the memory controller 202 viaseparate buses (not shown). The hard disk drive 208 and portable mediadrive 106 are connected to the memory controller via the PCI bus and anATA (AT Attachment) bus 216.

A 3D graphics processing unit 220 and a video encoder 222 form a videoprocessing pipeline for high speed and high resolution graphicsprocessing. Data carried from the graphics processing unit 220 to thevideo encoder 222 via a digital video bus (not shown). An audioprocessing unit 224 and an audio codec (coder/decoder) 226 form acorresponding audio processing pipeline with high fidelity and stereoprocessing. Audio data is carried between the audio processing unit 224and the audio codec 226 via a communication link (not shown). The videoand audio processing pipelines output data to an A/V (audio/video) port228 for transmission to the television or other display. In theillustrated implementation, the video and audio processing components220–228 are mounted on the module 214.

Also implemented on the module 214 are a USB host controller 230 and anetwork interface 232. The USB host controller 230 is coupled to the CPU200 and the memory controller 202 via a bus (e.g., PCI bus) and servesas host for the peripheral controllers 104(1)–104(4). The networkinterface 232 provides access to a network (e.g., Internet, homenetwork, etc.) and may be any of a wide variety of various wire orwireless interface components including an Ethernet card, a modem, aBluetooth module, a cable modem, and the like.

The game console 102 has two dual controller support subassemblies240(1) and 240(2), with each subassembly supporting two game controllers104(1)–104(4). A front panel I/O subassembly 242 supports thefunctionality of the power button 112 and the eject button 114, as wellas any LEDs (light emitting diodes) or other indicators exposed on theouter surface of the game console. The subassemblies 240(1), 240(2), and242 are coupled to the module 214 via one or more cable assemblies 244.

Eight memory units 140(1)–140(8) are illustrated as being connectable tothe four controllers 104(1)–104(4), i.e., two memory units for eachcontroller. Each memory unit 140 offers additional storage on whichgames, game parameters, and other data may be stored. When inserted intoa controller, the memory unit 140 can be accessed by the memorycontroller 202.

A system power supply module 250 provides power to the components of thegaming system 100. A fan 252 cools the circuitry within the game console102.

A console user interface (UI) application 260 is stored on the hard diskdrive 208. When the game console is powered on, various portions of theconsole application 260 are loaded into RAM 206 and/or caches 210, 212and executed on the CPU 200. The console application 260 presents agraphical user interface that provides a consistent user experience whennavigating to different media types available on the game console.

The game console 102 implements a cryptography engine to perform commoncryptographic functions, such as encryption, decryption, authentication,digital signing, hashing, and the like. The cryptography engine may beimplemented as part of the CPU 200, or in software stored on the harddisk drive 208 that executes on the CPU, so that the CPU is configuredto perform the cryptographic functions.

The gaming system 100 may be operated as a standalone system by simplyconnecting the system to a television or other display. In thisstandalone mode, the gaming system 100 allows one or more players toplay games, watch movies, or listen to music. However, with theintegration of broadband connectivity made available through the networkinterface 232, the gaming system 100 may further be operated as aparticipant in a larger network gaming community. This network gamingenvironment is described next.

Network Gaming

FIG. 3 shows an exemplary network gaming environment 300 thatinterconnects multiple gaming systems 100(1), . . . , 100(g) via anetwork 302. The network 302 represents any of a wide variety of datacommunications networks. It may include public portions (e.g., theInternet) as well as private portions (e.g., a residential Local AreaNetwork (LAN)), as well as combinations of public and private portions.Network 302 may be implemented using any one or more of a wide varietyof conventional communications media including both wired and wirelessmedia. Any of a wide variety of communications protocols can be used tocommunicate data via network 302, including both public and proprietaryprotocols. Examples of such protocols include TCP/IP, IPX/SPX, NetBEUI,etc.

In addition to gaming systems 100, one or more data centers may beaccessible via the network 302 to provide various services forparticipants. An exemplary data center 304 is illustrated as comprisingan authentication server 306 that registers individual gaming systems100 and one or more online servers 308(1), . . . , 308(s) to providevarious services, such as hosting online games, serving downloadablemusic or video files, hosting gaming competitions, serving streamingaudio/video files, and the like. The authentication server 306 hasaccess to a database 310 that stores manufacturing secrets placed onindividual gaming systems during manufacturing. These secrets are usedfor registering or authenticating the gaming systems prior to allowingthe gaming systems to participate in online gaming or other services.

While the authentication server 306, online servers 308, and database310 are logically grouped as forming the data center 304, it is notedthat the various computer systems may or may not be physically locatedtogether or as part of the same facility. Additionally, while theauthentication server 306 is illustrated separately from the onlineservers 308, the authentication functionality may be integrated as partof the services.

The network gaming environment 300 may further involve a keydistribution center 312 that plays a role in authenticating individualplayers and/or gaming systems 100 to one another as well as onlineservices 304. The distribution center 312 distributes keys and servicetickets to valid participants that may then be used to form gamesamongst multiple players or to purchase services from the onlineservices 308. The distribution center 312 may be integrated into thedata center 304 or reside independently, as shown.

To participate in online gaming (or other network services), the gamingsystems 100 first seek to be authenticated by the authentication server306. To grant permission to participate in online services, theauthentication server 306 needs to trust that each gaming system isgenuine and not an imposter computing device. Authentic gaming systems100 are manufactured with secrets that are stored in the database 310.The authentication server 306 uses these secrets to discern whether thegaming system 100 is genuine. The techniques for manufacturing gamingsystems that can be authenticated for online gaming over an opennetwork, such as the Internet, are described in the next section.

Once authenticated, the gaming systems can participate in online gamingor other services, or proceed to authenticate individual users with thekey distribution center. A multi-user authentication architecture isdescribed in more detail in U.S. patent application Ser. No. 09/802,795,entitled “Multiple User Authentication for Online Console-Based Gaming”,which was filed Mar. 9, 2001. This application is assigned to MicrosoftCorporation and is hereby incorporated by reference.

Manufacturing Authenticatable Gaming Systems

An architecture for manufacturing gaming systems is provided to addressthe console authentication problem. Simply stated, the problem is how anauthentication entity can be assured that the entity on the other sideof the network is an authentic game console. The architecture generallyinvolves storing secret, authenticatable data on the game console duringmanufacturing and maintaining corresponding verifying data at theauthentication entity. During registration, the authentication entityuses the verifying data to verify the authenticatable data submitted bythe game console to determine the authenticity of the game console. Tworepresentative architectures are described: (1) a symmetric keyarchitecture and (2) a public key architecture.

Symmetric Key Architecture

The symmetric key architecture involves writing a randomly generatedsymmetric key, along with a console ID, on the game console duringmanufacturing. This key/ID pair subsequently functions as apassword/name pair during registration to prove to the authenticationserver that the game console is authentic. The architecture is describedwith reference to FIGS. 4 and 5, where FIG. 4 illustrates themanufacturing process and FIG. 5 illustrates the registration process.

FIG. 4 shows an exemplary manufacturing process 400 in which a symmetrickey and a console ID are placed on the game console duringmanufacturing. For discussion purposes, the manufacturer operates one ormore manufacturing facilities, each of which includes one or moremanufacturing computing systems 450 and databases 452. The manufacturingdatabases are sometimes referred to as “genealogy databases”. Themanufacturing computing systems 450 are used to program, configure, orotherwise enable the software/firmware being placed in the gameconsoles.

At operation 402, a unique identifier Ni is assigned for eachmanufactured console 102(i). The console ID could be, for example, asequential number or the serial number of the manufactured console. Atoperation 404, a symmetric key Ki is randomly generated for console102(i). At operation 406, the symmetric key Ki and the consoleidentifier Ni are stored in a programmatically accessible non volatilememory of the console 102(i). The location of storage is preferablysecure and/or secret from access by the game console owner, but isotherwise programmatically accessible by authorized game code. Thepossible locations include, but are not limited to, an EEPROM, the harddrive, or flash ROM. The Ki/Ni pair may also be cryptographicallyprotected to further prevent access by the game console owner.

The Ki/Ni pair will be used during the registration process to prove tothe authenticity of the game console. Accordingly, the Ki/Ni pair iscollected during manufacturing for transport to the data center 304 thatis responsible for is registering the game console. However, thetransportation and storage of the key/ID pair introduce potential risksof discovery. To secure the symmetric keys for storage andtransportation, the symmetric key is encrypted with a transportationpublic key Kt_pub right after the symmetric key Ki is generated andstored in the game console (operation 408). The correspondingtransportation private key Kt_prv, which is used to decrypt and accessthe symmetric key Ki, is securely maintained at the data center 304 andis only accessed when used during registration of a game console.

It is noted that one or more of the operations 404–408 may be performedby the manufacturing computing systems 450, or alternatively by the gameconsoles themselves. Regardless of where the key Ki is generated andencrypted, the goal is to have the key exist in its raw state for asshort of time as possible. Minimizing this time will further enhancesecurity.

It is further noted that the symmetric key Ki may be encrypted usingcryptographic ciphers other than public key ciphers. For instance, thesymmetric key Ki may be encrypted using a symmetric key cipher, wherethe symmetric key is securely maintained at the manufacturer and thedata center.

At operation 410, the encrypted symmetric key (denoted as E(Kt_pub, Ki))is stored in the manufacturer database 452 along with the consoleidentifier Ni. At operation 412, the console identifier Ni and theencrypted symmetric key E(Kt_pub, Ki) for all manufactured consoles aretransferred, individually or in batch, from the manufacturer database452 to the data center 304. The information may be transferred accordingto any number of different techniques, including electronic transmissionover a network, secure portage on a portable storage media, or by othermeans.

At this point, the game consoles are finished being manufactured and arepackaged for distribution and sale. After the game consoles arepurchased, the owners may wish to participate in an online service, suchas gaming or downloading audio/video files. When the game consolesinitially encounter an online service, the game consoles perform aregistration process to prove its authenticity to the online service.For discussion purposes, suppose the game console registers with theauthentication server 306 of the data center 304 to enable participationin an online gaming event being hosted by one or more online servers308.

FIG. 5 shows an exemplary registration process 500 in which theauthentication server 306 at the data center 304 authenticates the gameconsole 102(i). At operation 502, the console 102(i) submits thesymmetric key (or proof of key knowledge) and the console ID pair (e.g.,Ki, Ni) to the authentication server 306 at the data center 304 as partof an authentication protocol. The symmetric key Ki is usually protectedin some manner during the authentication protocol, while the consoleidentifier Ni need not be. Many different authentication protocols canbe used during this operation, including (but not limited to) Kerberos,Digest, and HTTP Basic. The communication over the network can all beoptionally secured within a secure channel (e.g., SSL channel).

At operation 504, the authentication server 306 uses the consoleidentifier Ni to lookup the associated symmetric key in themanufacturer's secrets database 310. The result of the lookup produces adata record 520 for console 102(i). The data record 520 includes theencrypted symmetric key E(Kt_pub, Ki) originally created by andtransferred from the manufacturer in the manufacturing process 400 ofFIG. 4. At operation 506, the authentication server 306 decrypts thesymmetric key using the transportation private key Kt_prv stored at theauthentication server 306 to recover the symmetric key Ki.

At operation 508, the authentication server 306 verifies the credentialssubmitted by the game console 102(i) by, in part, comparing thesubmitted key Ki (or proof of its knowledge) with themanufacturer-assigned symmetric key Ki recovered from the record 520 inthe manufacturer's secrets database 310. The authentication servereither accepts or rejects the game console based on whether theauthentication succeeds or fails, which is based at least in part onwhether the two keys match.

At this point, the results of the authentication could be used todirectly allow/disallow participation in online services. In this case,the symmetric keys are used each time the game console requestsauthentication for purposes of participating in online services.Alternatively, the results of the authentication could be used tobootstrap a new credential process in which a new set of credentials aregenerated and transported back to the game console for use later duringonline service authentication. In this second case, the Ki/Ni pair isused only once for authentication during registration of the gameconsole and the registration process will return a new set ofcredentials to the console that can be used from then on.

The advantage of the symmetric key architecture is that no secrets aremaintained at the manufacturer. The secret transportation private key iskept at the data center. Thus, the opportunity for a cheater to stealthe secret is greatly diminished.

Public Key Architecture

The public key architecture involves writing a private key and a digitalcertificate into each game console during manufacturing. The certificatecontains the public key that matches the private key. The certificate issigned by a certification authority placed at each manufacturing site.Each certification authority certificate is further signed by anothercertificate that eventually leads up a certificate chain to a rootcertificate. Whenever a game console goes online to register itself, acertificate chain verification process along with proof of knowledge ofthe private key are used to authenticate the console as genuine. Thepublic key architecture is described with reference to FIGS. 6–8, whereFIG. 6 illustrates a pre-manufacturing process, FIG. 7 illustrates themanufacturing process, and FIG. 8 illustrates the registration process.

FIG. 6 shows an exemplary pre-manufacturing process 600 in which publickey pairs and chained certificates are generated. The process 600 may beperformed any time before the manufacturing of the game consoles 102. Itmay be performed at the manufacturing facility or elsewhere. Atoperation 602, a root public key pair consisting of a root public keyKroot_pub and a root private key Kroot_prv is generated. The root keypair is trusted and securely stored.

At operation 604, the root key pair is used to generate a rootcertificate CERT(Kroot_prv, Kroot_pub). The notation “CERT(Kroot_prv,Kroot_pub)” means that the root private key Kroot_prv is used todigitally sign a composite of the root public key Kroot_pub and apurpose statement vouching for the authenticity of the root public keyfor anyone knowing the corresponding root private key. Thus, anybodywith access to the root public key Kroot_pub should be able to verifythe authenticity of the certificate. One example type of certificate isan X.509 format certificate. However, other types of data structuresthat carry a public key signed by another private key can be considereda certificate.

At operation 606, a second public key pair is generated for use by acertification authority (CA) at the manufacturing site. This second keypair is referred to as the certification authority key pair (or CA keypair) and consists of a CA public key Kca_pub and a CA private keyKca_prv. If there is more than one certification authority at eachmanufacturing site, a different CA key pair is generated for eachcertification authority. Accordingly, each manufacturing site isassociated with one or more CA key pairs.

At operation 608, a CA certificate for the certification authority isgenerated and signed by the root private key Kroot_prv. The CAcertificate is designated as CERT(Kroot_prv, Kca_pub), meaning the rootprivate key Kroot_prv is used to digitally sign a composite of the CApublic key Kca_pub and a purpose statement vouching for the authenticityof the CA public key for anyone knowing the CA private key.

At operation 610, the CA certificate CERT(Kroot_prv, Kca_pub) and the CAprivate key are stored at the certification authority 650 at themanufacturing site. The CA certificate and the CA private key Kca_prvare securely maintained to prevent compromise. At operation 612, theroot public key Kroot_pub and/or the root certificate CERT(Kroot_prv,Kroot_pub) is transported (if generated remotely) and securely stored tothe data center 304.

FIG. 7 shows an exemplary manufacturing process 700 in which a privatekey and one or more certificates are placed on the game console duringmanufacturing. For purposes of manufacturing, the manufacturer maintainsthe CA public key pair (Kca_pub, Kca_prv) and the CA certificateCERT(Kroot_prv, Kca_pub).

At operation 702, a game console public key pair for each manufacturedconsole 102(i) is generated. The console public key pair consists of aconsole public key Ki_pub and a console private key Ki_prv. At operation704, a console certificate CERT(Kca_prv, Ki_pub) is generated and signedby the CA private key Kca_prv of the certification authority at thefactory. The console certificate contains the console public key Ki_puband vouches for its authenticity for anyone knowing the console privatekey Ki_prv.

At operation 706, the manufacturer records the console private keyKi_prv, the console certificate CERT(Kca_prv, Ki_pub), and CAcertificate CERT(Kroot_prv, Kca_pub) into the game console. The locationin storage is such that the key and certificates are programmaticallyaccessible by authorized game code, but secure from being accessed bythe game console owner. The possible locations include, but are notlimited to, an EEPROM, hard drive, or flashable ROM. While the CAprivate key Kca_prv is secured at the manufacturing site, all otherinformation including public keys and certificates can be freelydistributed without security measures.

FIG. 8 shows an exemplary registration process 800 in which the gameconsole is authenticated by the authentication server 306 at the datacenter 304. Many different public key authentication protocols can beemployed to implement the registration process. At the time ofregistration, the authentication server 306 has access to the rootcertificate (and thus root public key).

At operation 802, as part of one suitable protocol, the console 102(i)sends the console certificate CERT(Kca_prv, Ki_pub) to theauthentication server 306 at the data center 304. The console mayoptionally send the CA certificate CERT(Kroot_prv, Kca_pub) if theauthentication server does not already possess the CA certificateCERT(Kroot_prv, Kca_pub). The console also submits some proof that itknows the console private key Ki_prv. This proof can be achieved in manyways. One approach for providing such proof is to encrypt some datausing the console private key Ki_prv. This data may be, for example, thecurrent time, a random number, a message, etc. For purposes ofcontinuing discussion, assume the console encrypts the current time withthe console private key, or E(Ki_prv, CurrentTime). Using the currenttime can help thwart replay attacks.

Next, the authentication server 306 performs a certificate chainauthentication process to traverse the certificate chain out to theconsole certificate. More specifically, at operation 804, theauthentication server 306 authenticates the CA certificateCERT(Kroot_prv, Kca_pub) by verifying the signature of the CAcertificate using root public key Kroot_pub. The root public key may bestored at the authentication server or extracted from the rootcertificate CERT(Kroot_prv, Kroot_pub). At operation 806, theauthentication server 306 obtains the CA public key Kca_pub from the CAcertificate and uses it to verify the signature of the consolecertificate CERT(Kca_prv, Ki_pub), thereby authenticating the consolecertificate.

At operation 808, the authentication server 306 uses the console publickey Ki_pub retrieved from the console certificate to evaluate the proofof knowledge of the console private key Ki_prv. If the authenticationserver 306 can verify via the submitted proof that the console hasknowledge of the correct console private key, the game console 102(i) istrusted to be genuine. In our example of using current time, theauthentication server employs the console public key to decrypt theencrypted current time submitted by the console. The recovered currenttime is verified to be within an acceptable time skew. The game servereither accepts or rejects the game console based on whether theauthentication succeeds or fails, which is based at least in part onwhether the recovered time is within the time skew.

At this point, the results of the authentication could be used todirectly allow/disallow participation in online services. In this case,the same registration process is used each time the game consolerequests authentication for purposes of participating in onlineservices. Alternatively, the results of the authentication could be usedto bootstrap a new credential process in which a new set of credentialsare generated and transported back to the game console for use laterduring online service authentication. In this second case, the consoleprivate key Ki_prv, the console certificate CERT(Kca_prv, Ki_pub), andthe CA certificate CERT(Kroot_prv, Kca_pub) credentials are used onlyonce for authentication during registration and the registration processwill return a new set of credentials to the console that can be usedfrom then on.

It is noted that the public key architecture described herein employstwo levels of certificate chaining from the root certificate to theconsole certificate. More or fewer levels of certificate chaining may beused to deploy the architecture.

The advantage of the public key architecture is that no transfer of keystakes place between the console manufacturing sites and theauthentication server at the data center. However, with the public keyarchitecture, secrets are maintained at the manufacturer.

Conclusion

Although the invention has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the invention defined in the appended claims is not necessarilylimited to the specific features or acts described. Rather, the specificfeatures and acts are disclosed as exemplary forms of implementing theclaimed invention.

1. A method comprising: manufacturing a console-based gaming system withauthenticatable data stored in programmatically accessible memory, theauthenticatable data having corresponding verification data; andauthenticating the console-based gaming system for online participationin a gaming service by receiving the authenticatable data from theconsole-based gaming system and utilizing the verification data toverify the authenticatable data.
 2. A method as recited in claim 1,wherein the authenticatable data comprises a symmetric key used in asymmetric cryptographic cipher.
 3. A method as recited in claim 1,wherein the authenticatable data comprises a private key used in apublic key cryptographic cipher.
 4. A method as recited in claim 1,wherein the manufacturing comprises: storing a symmetric key and aconsole ID in the console-based gaming system; encrypting the symmetrickey to produce an encrypted symmetric key; and storing the encryptedsymmetric key and the console ID at an authentication entity employed toauthenticate the console-based gaming system.
 5. A method as recited inclaim 4, wherein the encrypting comprises encrypting the symmetric keyusing a public key cipher and a public key from a public key pair.
 6. Amethod as recited in claim 4, wherein the encrypting comprisesencrypting the symmetric key using a symmetric key cipher.
 7. A methodas recited in claim 4, wherein the authenticating comprises: receivingthe symmetric key and the console ID from the console-based gamingsystem; using the console ID to locate the encrypted symmetric key atthe authentication entity; decrypting the encrypted symmetric key usingthe public key cipher and a corresponding private key from the publickey pair to recover the symmetric key; and evaluating the symmetric keyrecovered from the encrypted symmetric key with the symmetric keyreceived from the console-based gaming system as a basis forauthenticating the console-based gaming system.
 8. A method as recitedin claim 1, wherein the manufacturing comprises: storing, on theconsole-based gaming system, a console private key unique to theconsole-based gaming system and at least one console certificate that ispart of a certificate chain chaining from a root certificate signed by aroot private key, to the console certificate containing a console publickey that corresponds to the console private key; and storing the rootpublic key at an authentication entity employed to authenticate theconsole-based gaming system.
 9. A method as recited in claim 8, whereinthe authenticating comprises: receiving the console certificate andproof of knowledge of the console private key from the console-basedgaming system; traversing the certificate chain to verify the consolecertificate and recover the console public key; and using the consolepublic key to evaluate the proof of knowledge of the console privatekey.
 10. One or more computer-readable media comprisingcomputer-executable instructions that, when executed, perform the methodas recited in claim
 1. 11. A method comprising: manufacturing a gameconsole that includes a symmetric key stored in programmaticallyaccessible memory; and using symmetric key cryptography to verify thesymmetric key on the game console as a basis for authenticating the gameconsole for online participation in a gaming service.
 12. A method asrecited in claim 11, wherein the manufacturing comprises: encrypting thesymmetric key to produce an encrypted symmetric key; and maintaining theencrypted symmetric key at an authentication entity employed toauthenticate the game console.
 13. A method as recited in claim 12,wherein the using comprises: receiving a proffered symmetric key fromthe game console; decrypting the encrypted symmetric key maintained atthe authentication entity; and evaluating the symmetric key recoveredfrom the encrypted symmetric key with the proffered symmetric keyreceived from the game console.
 14. A method as recited in claim 11,wherein the manufacturing comprises: encrypting the symmetric key usinga public key cipher and a public key from a public key pair to producean encrypted symmetric key; and maintaining the encrypted symmetric keyat an authentication entity employed to authenticate the game console.15. A method as recited in claim 14, wherein the using comprises:receiving a proffered symmetric key from the game console; decryptingthe encrypted symmetric key maintained at the authentication entityusing the public key cipher and a private key from the public key pairto recover the symmetric key; and evaluating the symmetric key recoveredfrom the encrypted symmetric key with the proffered symmetric keyreceived from the game console.
 16. A method comprising: manufacturing agame console that stores a verifiable certificate and a private key froma public key pair in programmatically accessible memory; and usingpublic key cryptography to verify the verifiable certificate and theprivate key of the game console as a basis for authenticating the gameconsole for online participation in a gaming service.
 17. A method asrecited in claim 16, wherein the manufacturing comprises: generating aroot public key pair having a root public key and a corresponding rootprivate key; generating a certificate chain from a root certificatesigned by the root private key to the verifiable certificate, theverifiable certificate containing a corresponding public key from thepublic key pair; and writing the verifiable certificate and the privatekey into the programmatically accessible memory.
 18. A method as recitedin claim 17, wherein the using comprises: receiving the verifiablecertificate and proof of knowledge of the private key from the gameconsole; traversing the certificate chain to verify the verifiablecertificate and recover the public key; and using the public key toevaluate the proof of knowledge of the private key.
 19. A methodcomprising: during manufacturing: assigning a console ID to each gameconsole; randomly generating a symmetric key; storing the symmetric keyand the console ID in programmatically accessible memory in the gameconsole; encrypting the symmetric key using a public key of a public keypair to produce an encrypted symmetric key; maintaining the encryptedsymmetric key and the console ID in a database; transferring theencrypted symmetric key and the console ID to a data center; duringregistration of the game console at the data center: receiving aproffered symmetric key and the console ID from the game console;locating a record using the console ID received from the game console,the record containing the encrypted symmetric key; decrypting theencrypted symmetric key using the public key cipher and a private keyfrom the public key pair to recover the symmetric key; and evaluatingthe symmetric key recovered from the encrypted symmetric key with theproffered symmetric key received from the game console as a basis forauthenticating the game console for online participation in a gamingservice.
 20. A method comprising: prior to registration: generating aroot public key pair having a root public key and a corresponding rootprivate key; generating a root certificate that contains the root publickey and is signed by the root private key; generating a certificationauthority (CA) public key pair having a CA public key and acorresponding CA private key; generating a CA certificate that containsthe CA public key and is signed by the root private key; generating aconsole public key pair having a console public key and a correspondingconsole private key; generating a console certificate that contains theconsole public key and is signed by the CA private key; storing theconsole certificate and the console private key in programmaticallyaccessible memory of a game console; during registration: receiving theconsole certificate and proof of knowledge of the console private keyfrom the game console; using the root public key to verify the CAcertificate and recover the CA public key; using the CA public key toverify the console certificate and recover the console public key; andusing the console public key to evaluate the proof of knowledge of theconsole private key received from the game console for onlineparticipation in a gaming service.
 21. A systems comprising: amanufacturing-based computing system configured to write authenticatabledata into programmatically accessible memory of a game console, theauthenticatable data having corresponding verification data maintainedseparately from the game console; and an authentication computing systemconfigured to authenticate the game console for online participation ina gaming service by receiving the authenticatable data from the gameconsole and utilizing the verification data to verify theauthenticatable data.
 22. A system, comprising: a manufacturing-basedcomputing system configured to write a randomly generated symmetric keyand a console ID into a programmatically accessible memory in the gameconsole, the manufacturing-based computing system further storing thesymmetric key in encrypted form; and an authentication computing systemconfigured to authenticate the game console by receiving a profferedsymmetric key and the console ID from the game console, theauthentication computing system using the console ID to locate thesymmetric key in encrypted form and then decrypting the symmetric key,the authentication computing system using the symmetric key to evaluatethe proffered symmetric key received from the game console as a basisfor authenticating the game console for online participation in a gamingservice.
 23. A system, comprising: a manufacturing-based computingsystem configured to write a console certificate and a console privatekey into programmatically accessible memory of the game console, theconsole certificate being part of a certificate chain starting from aroot certificate signed by a root private key, leading to the consolecertificate containing a console public key associated with the consoleprivate key; and an authentication computing system configured toauthenticate the game console by verifying a proffered consolecertificate submitted by the game console using the certificate chain,the authentication computing system using the console public key fromthe console certificate to evaluate proof of knowledge of the consoleprivate key submitted by the game console for online participation in atraining service.
 24. A system, comprising: writing means for writing anoriginal symmetric key and a console ID into programmatically accessiblememory of a game console; encryption means for encrypting the originalsymmetric key using a public key of a public key pair to produce anencrypted symmetric key; storage means for maintaining the encryptedsymmetric key separately from the game console; and authentication meansfor authenticating the game console by comparing a proffered symmetrickey submitted by the game console with the original symmetric keydecrypted from the encrypted symmetric key to determine if the proposedsymmetric key matches the original symmetric key for onlineparticipation in a gaming service.
 25. A system, comprising: certificategeneration means for generating a certificate chain from a rootcertificate signed by a root private key to a console certificateassociated with a game console, the console certificate containing aconsole public key from a console public key pair, writing means forwriting the console certificate and a console private key from theconsole public key pair in programmatically accessible memory of thegame console; and authentication means for authenticating the gameconsole by verifying a proffered console certificate submitted by thegame console using the certificate chain and if valid, extracting theconsole public key from the console certificate to evaluate proof ofknowledge of the console private key submitted by the game console foronline participation in a gaming service.